Job definition - Actions & options

Job definition actions are automated actions or options that arise at various stages of a job’s life cycle. Actions involving the template are created in Template actions.

An action could be something like “send an e-mail to the assigned engineer when a job is allocated” or they could be something like “if a job is at the status of ‘awaiting invoicing’ then give the user an option to mark it as invoiced”.

Here is a list of statuses in the job's lifecycle that can have actions/options assigned to them. Supplementary statuses can also have actions/options assigned to them.

Click on these links to see what the actions/options do

E-mail notification	Create sub-job	Status update
Triggered update	Manually close	Activate job
SMS text notification

Option within job screen	Additional action buttons can be added to the existing ones at the bottom of the job screens using this option. This means that the actions are triggered manually and a common example of this is to manually close a job.
When a job is assigned	A job is given a status of 'assigned' when it has been allocated to a user and it appears on their device. This is equivalent to allocated or outstanding in the menu lists.
When a job is re-assigned	A job is re-assigned when the user to whom it is allocated is changed. This also triggers assigned and de-assigned actions.
When a job is de-assigned	A job is de-assigned when a job is taken away from a user. This is triggered as part of the re-assigned status change.
When job details are changed	These actions will be triggered when the job details are changed. If the user is changed, assigned, re-assigned and de-assigned actions may also be triggered.
When a job is manually closed	These actions will be triggered by using a button set up in 'Option within job screen' (see above) that has an action of Manually close job.
When a job has a status change (pre-work)	These actions will be triggered when a supplementary status is changed prior to the job being allocated to a user. Once the job has been allocated/assigned and sent to the device this will not be triggered.
When a job has a status change (post-work)	These actions will be triggered when a supplementary status is changed after the job has been completed by a user. Until the job has been sent back from the device this will not be triggered.